This is a multi-part message in MIME format.
--===============1803911681==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01C82C7D.B09FC4E7"
This is a multi-part message in MIME format.
------_=_NextPart_001_01C82C7D.B09FC4E7
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
All,
We have an OO perl framework here that utilizes Win32::SerialPort to
automate configuration of various network devices. One of the things we
like to do is capture device state; as a result on occasion we generate
alot of data that's piped through the console. We've noticed there are
issues with Win32::SerialPort choking while processing this data.
Another problem we've got is that our Perl scripts also seem to "forget"
it's got COM ports open. On occasion when we have a PORT_OBJ instance
saved as an object's property, that property may be nulled out for some
unknown reason during execution, and this behavior cannot be reliably
replicated.
I was wondering if there was some alternative to using SerialPort.
Would WMI be something we could look into? Is there any Perl code
available that could do TCP->Serial mapping?
- Joe
------_=_NextPart_001_01C82C7D.B09FC4E7
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.6000.16544" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D163230520-21112007><FONT face=3DArial
size=3D2>All,</FONT></SPAN></DIV>
<DIV><SPAN class=3D163230520-21112007><FONT face=3DArial
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D163230520-21112007><FONT face=3DArial size=3D2>We =
have an OO perl
framework here that utilizes Win32::SerialPort to =
automate configuration
of various network devices. One of the things we like to do =
is
capture device state; as a result on occasion we generate alot of data =
that's
piped through the console. We've noticed there are issues with
Win32::SerialPort choking while processing this data. Another =
problem
we've got is that our Perl scripts also seem to "forget" it's got COM =
ports
open. On occasion when we have a PORT_OBJ instance saved =
as an
object's property, that property may be nulled out for some unknown =
reason
during execution, and this behavior cannot be reliably
replicated.</FONT></SPAN></DIV>
<DIV><SPAN class=3D163230520-21112007><FONT face=3DArial
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D163230520-21112007><FONT face=3DArial size=3D2>I was =
wondering if
there was some alternative to using SerialPort. Would WMI be =
something we
could look into? Is there any Perl code available that could do
TCP->Serial mapping?</FONT></SPAN></DIV>
<DIV><SPAN class=3D163230520-21112007><FONT face=3DArial
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D163230520-21112007><FONT face=3DArial =
size=3D2> -
Joe</FONT></SPAN></DIV></BODY></HTML>
------_=_NextPart_001_01C82C7D.B09FC4E7--
--===============1803911681==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
ActivePerl mailing list
ActivePerl [at] listserv.ActiveState.com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
--===============1803911681==--
